-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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]: Failed to search: node offline[node=-1]: channel not available when streamingDeltaForwardPolicy
is Direct
#36887
Labels
deletion-opt
kind/bug
Issues or changes related a bug
priority/critical-urgent
Highest priority. Must be actively worked on as someone's top priority right now.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Milestone
Comments
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
Oct 15, 2024
ThreadDao
added
the
priority/critical-urgent
Highest priority. Must be actively worked on as someone's top priority right now.
label
Oct 15, 2024
/unassign |
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
Oct 16, 2024
congqixia
added a commit
to congqixia/milvus
that referenced
this issue
Oct 16, 2024
Related to milvus-io#36887 Forward delete to L0 segment will return error and mark l0 segment offline causing delegator unserviceable Signed-off-by: Congqi Xia <[email protected]>
sre-ci-robot
pushed a commit
that referenced
this issue
Oct 16, 2024
Related to #36887 Forward delete to L0 segment will return error and mark l0 segment offline causing delegator unserviceable Signed-off-by: Congqi Xia <[email protected]>
congqixia
added a commit
to congqixia/milvus
that referenced
this issue
Oct 16, 2024
Related to milvus-io#36887 Forward delete to L0 segment will return error and mark l0 segment offline causing delegator unserviceable Signed-off-by: Congqi Xia <[email protected]>
sre-ci-robot
pushed a commit
that referenced
this issue
Oct 17, 2024
Cherry-pick from master pr: #36899 Related to #36887 Forward delete to L0 segment will return error and mark l0 segment offline causing delegator unserviceable Signed-off-by: Congqi Xia <[email protected]>
search failed fixed, but deletegator and 2 querynodes oom
|
seems that it hits quota limitation and shouldn't be OOMed? The OOM happened after "memory quota exceeded" log? |
congqixia
added a commit
to congqixia/milvus
that referenced
this issue
Oct 22, 2024
Related to milvus-io#36887 Signed-off-by: Congqi Xia <[email protected]>
congqixia
added a commit
to congqixia/milvus
that referenced
this issue
Oct 22, 2024
Related to milvus-io#36887 Signed-off-by: Congqi Xia <[email protected]>
sre-ci-robot
pushed a commit
that referenced
this issue
Oct 22, 2024
Rewritten based on master pr pr: #37043 Related to #36887 Signed-off-by: Congqi Xia <[email protected]>
sre-ci-robot
pushed a commit
that referenced
this issue
Oct 22, 2024
Related to #36887 Signed-off-by: Congqi Xia <[email protected]>
congqixia
added a commit
to congqixia/milvus
that referenced
this issue
Oct 23, 2024
Relatedt milvus-io#36887 DirectFoward streaming delete will cause memory usage explode if the segments number was large. This PR add batching delete API and using it for direct forward implementation. Signed-off-by: Congqi Xia <[email protected]>
sre-ci-robot
pushed a commit
that referenced
this issue
Oct 24, 2024
Relatedt #36887 DirectFoward streaming delete will cause memory usage explode if the segments number was large. This PR add batching delete API and using it for direct forward implementation. Signed-off-by: Congqi Xia <[email protected]>
congqixia
added a commit
to congqixia/milvus
that referenced
this issue
Oct 24, 2024
Relatedt milvus-io#36887 DirectFoward streaming delete will cause memory usage explode if the segments number was large. This PR add batching delete API and using it for direct forward implementation. Signed-off-by: Congqi Xia <[email protected]>
sre-ci-robot
pushed a commit
that referenced
this issue
Oct 25, 2024
…#37107) Cherry pick from master pr: #37076 Related #36887 DirectFoward streaming delete will cause memory usage explode if the segments number was large. This PR add batching delete API and using it for direct forward implementation. Signed-off-by: Congqi Xia <[email protected]>
congqixia
added a commit
to congqixia/milvus
that referenced
this issue
Oct 28, 2024
Related to milvus-io#36887 `LoadDeltaLogs` API did not check memory usage. When system is under high delete load pressure, this could result into OOM quit. This PR add resource check for `LoadDeltaLogs` actions and separate internal deltalog loading function with public one. Signed-off-by: Congqi Xia <[email protected]>
congqixia
added a commit
to congqixia/milvus
that referenced
this issue
Oct 28, 2024
Related to milvus-io#36887 Previously using newly create pool per request shall cause goroutine leakage. This PR change this behavior by using singleton delete pool. This change could also provide better concurrency control over delete memory usage. Signed-off-by: Congqi Xia <[email protected]>
congqixia
added a commit
to congqixia/milvus
that referenced
this issue
Oct 28, 2024
Related to milvus-io#36887 Previously using newly create pool per request shall cause goroutine leakage. This PR change this behavior by using singleton delete pool. This change could also provide better concurrency control over delete memory usage. Signed-off-by: Congqi Xia <[email protected]>
sre-ci-robot
pushed a commit
that referenced
this issue
Oct 29, 2024
Related to #36887 Previously using newly create pool per request shall cause goroutine leakage. This PR change this behavior by using singleton delete pool. This change could also provide better concurrency control over delete memory usage. Signed-off-by: Congqi Xia <[email protected]>
sre-ci-robot
pushed a commit
that referenced
this issue
Oct 29, 2024
Related to #36887 `LoadDeltaLogs` API did not check memory usage. When system is under high delete load pressure, this could result into OOM quit. This PR add resource check for `LoadDeltaLogs` actions and separate internal deltalog loading function with public one. --------- Signed-off-by: Congqi Xia <[email protected]>
congqixia
added a commit
to congqixia/milvus
that referenced
this issue
Oct 29, 2024
Related to milvus-io#36887 `LoadDeltaLogs` API did not check memory usage. When system is under high delete load pressure, this could result into OOM quit. This PR add resource check for `LoadDeltaLogs` actions and separate internal deltalog loading function with public one. --------- Signed-off-by: Congqi Xia <[email protected]>
congqixia
added a commit
to congqixia/milvus
that referenced
this issue
Oct 29, 2024
…#37220) Related to milvus-io#36887 Previously using newly create pool per request shall cause goroutine leakage. This PR change this behavior by using singleton delete pool. This change could also provide better concurrency control over delete memory usage. Signed-off-by: Congqi Xia <[email protected]>
sre-ci-robot
pushed a commit
that referenced
this issue
Oct 29, 2024
) Cherry-pick from master pr: #37220 Related to #36887 Previously using newly create pool per request shall cause goroutine leakage. This PR change this behavior by using singleton delete pool. This change could also provide better concurrency control over delete memory usage. Signed-off-by: Congqi Xia <[email protected]>
sre-ci-robot
pushed a commit
that referenced
this issue
Oct 29, 2024
) (#37233) Cherry pick from master pr: #37220 Related to #36887 Previously using newly create pool per request shall cause goroutine leakage. This PR change this behavior by using singleton delete pool. This change could also provide better concurrency control over delete memory usage. Signed-off-by: Congqi Xia <[email protected]>
congqixia
added a commit
to congqixia/milvus
that referenced
this issue
Oct 29, 2024
Related to milvus-io#36887 `LoadDeltaLogs` API did not check memory usage. When system is under high delete load pressure, this could result into OOM quit. This PR add resource check for `LoadDeltaLogs` actions and separate internal deltalog loading function with public one. --------- Signed-off-by: Congqi Xia <[email protected]>
sre-ci-robot
pushed a commit
that referenced
this issue
Oct 30, 2024
Cherry pick from master pr: #37195 Related to #36887 `LoadDeltaLogs` API did not check memory usage. When system is under high delete load pressure, this could result into OOM quit. This PR add resource check for `LoadDeltaLogs` actions and separate internal deltalog loading function with public one. --------- Signed-off-by: Congqi Xia <[email protected]>
sre-ci-robot
pushed a commit
that referenced
this issue
Oct 30, 2024
Cherry pick from master pr: #37195 Related to #36887 `LoadDeltaLogs` API did not check memory usage. When system is under high delete load pressure, this could result into OOM quit. This PR add resource check for `LoadDeltaLogs` actions and separate internal deltalog loading function with public one. --------- Signed-off-by: Congqi Xia <[email protected]>
congqixia
added a commit
to congqixia/milvus
that referenced
this issue
Oct 30, 2024
Related to milvus-io#36887 Remove non-hit pk delete record logic does not work since `insert_record_.contain` does not work due to logic problem. Signed-off-by: Congqi Xia <[email protected]>
congqixia
added a commit
to congqixia/milvus
that referenced
this issue
Oct 30, 2024
Related to milvus-io#36887 Remove non-hit pk delete record logic does not work since `insert_record_.contain` does not work due to logic problem. Signed-off-by: Congqi Xia <[email protected]>
sre-ci-robot
pushed a commit
that referenced
this issue
Oct 30, 2024
Cherry pick from master pr: #37305 Related to #36887 Remove non-hit pk delete record logic does not work since `insert_record_.contain` does not work due to logic problem. Signed-off-by: Congqi Xia <[email protected]>
sre-ci-robot
pushed a commit
that referenced
this issue
Oct 30, 2024
Related to #36887 Remove non-hit pk delete record logic does not work since `insert_record_.contain` does not work due to logic problem. Signed-off-by: Congqi Xia <[email protected]>
congqixia
added a commit
to congqixia/milvus
that referenced
this issue
Oct 30, 2024
Related to milvus-io#36887 Remove non-hit pk delete record logic does not work since `insert_record_.contain` does not work due to logic problem. Signed-off-by: Congqi Xia <[email protected]>
xiaofan-luan
pushed a commit
to xiaofan-luan/milvus
that referenced
this issue
Oct 30, 2024
Related to milvus-io#36887 Remove non-hit pk delete record logic does not work since `insert_record_.contain` does not work due to logic problem. Signed-off-by: Congqi Xia <[email protected]>
xiaofan-luan
pushed a commit
to xiaofan-luan/milvus
that referenced
this issue
Oct 30, 2024
Related to milvus-io#36887 Remove non-hit pk delete record logic does not work since `insert_record_.contain` does not work due to logic problem. Signed-off-by: Congqi Xia <[email protected]>
sre-ci-robot
pushed a commit
that referenced
this issue
Oct 31, 2024
Cherry pick from master pr: #37305 Related to #36887 Remove non-hit pk delete record logic does not work since `insert_record_.contain` does not work due to logic problem. Signed-off-by: Congqi Xia <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
deletion-opt
kind/bug
Issues or changes related a bug
priority/critical-urgent
Highest priority. Must be actively worked on as someone's top priority right now.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Is there an existing issue for this?
Environment
Current Behavior
milvus cluster
deploy a milvus with config
test steps
client delete log:
Expected Behavior
No response
Steps To Reproduce
compact-opt-100m-2-milvus-datanode-74b5c7854b-xxcdl 1/1 Running 0 3h53m 10.104.14.7 4am-node18
compact-opt-100m-2-milvus-indexnode-6cd9b49f5-9xtfj 1/1 Running 0 3h52m 10.104.4.36 4am-node11
compact-opt-100m-2-milvus-indexnode-6cd9b49f5-qb26s 1/1 Running 0 3h53m 10.104.17.2 4am-node23
compact-opt-100m-2-milvus-indexnode-6cd9b49f5-zp5bj 1/1 Running 0 3h51m 10.104.1.234 4am-node10
compact-opt-100m-2-milvus-mixcoord-8f9875d6d-khsb4 1/1 Running 0 3h53m 10.104.4.33 4am-node11
compact-opt-100m-2-milvus-proxy-5bd9875bb4-tkrzw 1/1 Running 0 3h53m 10.104.9.107 4am-node14
compact-opt-100m-2-milvus-querynode-0-7488f76b9b-8dz69 1/1 Running 0 3h52m 10.104.20.48 4am-node22
compact-opt-100m-2-milvus-querynode-0-7488f76b9b-dqwzf 1/1 Running 0 3h49m 10.104.23.93 4am-node27
compact-opt-100m-2-milvus-querynode-0-7488f76b9b-hs6hn 1/1 Running 0 3h53m 10.104.24.147 4am-node29
compact-opt-100m-2-milvus-querynode-0-7488f76b9b-p5dcv 1/1 Running 0 3h50m 10.104.30.192 4am-node38
The text was updated successfully, but these errors were encountered: