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]: search/query/index's rto is about 30s during rolling update from v2.4.5 to 2.4-20240709-737bd7c7-amd64 #34553

Open
1 task done
zhuwenxing opened this issue Jul 10, 2024 · 6 comments
Assignees
Labels
kind/bug Issues or changes related a bug severity/critical Critical, lead to crash, data missing, wrong result, function totally doesn't work. test/rolling-update triage/accepted Indicates an issue or PR is ready to be actively worked on.
Milestone

Comments

@zhuwenxing
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version:v2.4.5 to 2.4-20240709-737bd7c7-amd64
- Deployment mode(standalone or cluster):mixcoord
- MQ type(rocksmq, pulsar or kafka): kafka   
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS): 
- CPU/Memory: 
- GPU: 
- Others:

Current Behavior

[2024-07-09T17:36:19.548Z] FAILED testcases/test_single_request_operation_for_rolling_update.py::TestOperations::test_operations - pytest_assume.plugin.FailedAssumption: 

[2024-07-09T17:36:19.548Z] 3 Failed Assumptions:

[2024-07-09T17:36:19.548Z] 

[2024-07-09T17:36:19.548Z] testcases/test_single_request_operation_for_rolling_update.py:153: AssumptionFailure

[2024-07-09T17:36:19.548Z] >>	pytest.assume(rto <= rto_threshold,  f"{k} rto expect {rto_threshold}s but get {rto}s")

[2024-07-09T17:36:19.548Z] AssertionError: Op.index rto expect 10s but get 29.904550552368164s

[2024-07-09T17:36:19.548Z] assert False

[2024-07-09T17:36:19.548Z] 

[2024-07-09T17:36:19.548Z] testcases/test_single_request_operation_for_rolling_update.py:153: AssumptionFailure

[2024-07-09T17:36:19.548Z] >>	pytest.assume(rto <= rto_threshold,  f"{k} rto expect {rto_threshold}s but get {rto}s")

[2024-07-09T17:36:19.548Z] AssertionError: Op.search rto expect 10s but get 37.48464107513428s

[2024-07-09T17:36:19.548Z] assert False

[2024-07-09T17:36:19.548Z] 

[2024-07-09T17:36:19.548Z] testcases/test_single_request_operation_for_rolling_update.py:153: AssumptionFailure

[2024-07-09T17:36:19.548Z] >>	pytest.assume(rto <= rto_threshold,  f"{k} rto expect {rto_threshold}s but get {rto}s")

[2024-07-09T17:36:19.548Z] AssertionError: Op.query rto expect 10s but get 38.71662878990173s

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

failed job: https://qa-jenkins.milvus.io/blue/organizations/jenkins/rolling_update_for_operator_test_simple/detail/rolling_update_for_operator_test_simple/4045/pipeline

log:artifacts-kafka-mixcoord-4045-server-logs.tar.gz

cluster: 4am
namespace: chaos-testing
release name: kafka-mixcoord-4045

pod info

[2024-07-09T17:36:29.700Z] + kubectl get pods -o wide

[2024-07-09T17:36:29.795Z] + grep kafka-mixcoord-4045

[2024-07-09T17:36:30.354Z] kafka-mixcoord-4045-etcd-0                                       1/1     Running            0               39m     10.104.15.191   4am-node20   <none>           <none>

[2024-07-09T17:36:30.354Z] kafka-mixcoord-4045-etcd-1                                       1/1     Running            0               39m     10.104.25.214   4am-node30   <none>           <none>

[2024-07-09T17:36:30.354Z] kafka-mixcoord-4045-etcd-2                                       1/1     Running            0               39m     10.104.26.168   4am-node32   <none>           <none>

[2024-07-09T17:36:30.354Z] kafka-mixcoord-4045-kafka-0                                      2/2     Running            0               39m     10.104.15.193   4am-node20   <none>           <none>

[2024-07-09T17:36:30.354Z] kafka-mixcoord-4045-kafka-1                                      2/2     Running            0               39m     10.104.25.217   4am-node30   <none>           <none>

[2024-07-09T17:36:30.354Z] kafka-mixcoord-4045-kafka-2                                      2/2     Running            0               39m     10.104.26.172   4am-node32   <none>           <none>

[2024-07-09T17:36:30.354Z] kafka-mixcoord-4045-kafka-exporter-55b5558df4-l5tfh              1/1     Running            4 (38m ago)     39m     10.104.13.85    4am-node16   <none>           <none>

[2024-07-09T17:36:30.354Z] kafka-mixcoord-4045-kafka-zookeeper-0                            1/1     Running            0               39m     10.104.15.192   4am-node20   <none>           <none>

[2024-07-09T17:36:30.354Z] kafka-mixcoord-4045-kafka-zookeeper-1                            1/1     Running            0               39m     10.104.25.218   4am-node30   <none>           <none>

[2024-07-09T17:36:30.354Z] kafka-mixcoord-4045-kafka-zookeeper-2                            1/1     Running            0               39m     10.104.26.171   4am-node32   <none>           <none>

[2024-07-09T17:36:30.354Z] kafka-mixcoord-4045-milvus-datanode-6857458c4-8wtd6              1/1     Running            0               22m     10.104.5.164    4am-node12   <none>           <none>

[2024-07-09T17:36:30.354Z] kafka-mixcoord-4045-milvus-datanode-6857458c4-ncc5s              1/1     Running            0               23m     10.104.21.8     4am-node24   <none>           <none>

[2024-07-09T17:36:30.354Z] kafka-mixcoord-4045-milvus-datanode-6857458c4-rfbb5              1/1     Running            0               21m     10.104.32.214   4am-node39   <none>           <none>

[2024-07-09T17:36:30.354Z] kafka-mixcoord-4045-milvus-indexnode-9d59cf5b-5q8kd              1/1     Running            0               28m     10.104.5.140    4am-node12   <none>           <none>

[2024-07-09T17:36:30.354Z] kafka-mixcoord-4045-milvus-indexnode-9d59cf5b-mp8pt              1/1     Running            0               29m     10.104.4.53     4am-node11   <none>           <none>

[2024-07-09T17:36:30.354Z] kafka-mixcoord-4045-milvus-indexnode-9d59cf5b-xz64h              1/1     Running            0               30m     10.104.14.159   4am-node18   <none>           <none>

[2024-07-09T17:36:30.354Z] kafka-mixcoord-4045-milvus-mixcoord-58965bf778-9sq79             1/1     Running            0               26m     10.104.13.102   4am-node16   <none>           <none>

[2024-07-09T17:36:30.354Z] kafka-mixcoord-4045-milvus-proxy-67bf7bbd48-c995f                1/1     Running            0               21m     10.104.32.213   4am-node39   <none>           <none>

[2024-07-09T17:36:30.354Z] kafka-mixcoord-4045-milvus-querynode-1-7b7c9b658b-9mt9p          1/1     Running            0               23m     10.104.21.7     4am-node24   <none>           <none>

[2024-07-09T17:36:30.354Z] kafka-mixcoord-4045-milvus-querynode-1-7b7c9b658b-l8fv5          1/1     Running            0               22m     10.104.24.148   4am-node29   <none>           <none>

[2024-07-09T17:36:30.354Z] kafka-mixcoord-4045-milvus-querynode-1-7b7c9b658b-vqjmk          1/1     Running            0               24m     10.104.32.211   4am-node39   <none>           <none>

[2024-07-09T17:36:30.354Z] kafka-mixcoord-4045-minio-0                                      1/1     Running            0               39m     10.104.15.190   4am-node20   <none>           <none>

[2024-07-09T17:36:30.354Z] kafka-mixcoord-4045-minio-1                                      1/1     Running            0               39m     10.104.25.213   4am-node30   <none>           <none>

[2024-07-09T17:36:30.354Z] kafka-mixcoord-4045-minio-2                                      1/1     Running            0               39m     10.104.26.166   4am-node32   <none>           <none>

[2024-07-09T17:36:30.354Z] kafka-mixcoord-4045-minio-3                                      1/1     Running            0               39m     10.104.17.127   4am-node23   <none>           <none>

Anything else?

No response

@zhuwenxing zhuwenxing 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 Jul 10, 2024
@zhuwenxing zhuwenxing added this to the 2.4.6 milestone Jul 10, 2024
@zhuwenxing
Copy link
Contributor Author

standalone and cluster modes work well for same update path

@yanliang567
Copy link
Contributor

/assign @weiliu1031
/unassign

@yanliang567 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 Jul 10, 2024
@zhuwenxing zhuwenxing added priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. severity/critical Critical, lead to crash, data missing, wrong result, function totally doesn't work. labels Jul 12, 2024
@yanliang567 yanliang567 modified the milestones: 2.4.6, 2.4.7 Jul 19, 2024
@yanliang567
Copy link
Contributor

not reproduce recently, lower the priority

@yanliang567 yanliang567 removed priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. severity/critical Critical, lead to crash, data missing, wrong result, function totally doesn't work. labels Jul 22, 2024
@zhuwenxing zhuwenxing added priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. severity/critical Critical, lead to crash, data missing, wrong result, function totally doesn't work. test/rolling-update labels Jul 24, 2024
@weiliu1031
Copy link
Contributor

after balance channel, new delegator hasn't consume to latest ts, if search with strong consistency, then it may failed due to wait tSafe until timeout

@yanliang567 yanliang567 removed the priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. label Jul 25, 2024
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 severity/critical Critical, lead to crash, data missing, wrong result, function totally doesn't work. test/rolling-update triage/accepted Indicates an issue or PR is ready to be actively worked on.
3 participants