-
Notifications
You must be signed in to change notification settings - Fork 3.7k
Closed
Labels
feature/streaming nodestreaming node featurestreaming node featurekind/bugIssues or changes related a bugIssues or changes related a bugseverity/criticalCritical, lead to crash, data missing, wrong result, function totally doesn't work.Critical, lead to crash, data missing, wrong result, function totally doesn't work.triage/acceptedIndicates an issue or PR is ready to be actively worked on.Indicates an issue or PR is ready to be actively worked on.
Milestone
Description
Is there an existing issue for this?
- I have searched the existing issues
Environment
- Milvus version: chyezh-enhance_make_recovery_components_full_debug-76b08a2-20250509
- Deployment mode(standalone or cluster): standalone
- MQ type(rocksmq, pulsar or kafka):
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS):
- CPU/Memory:
- GPU:
- Others:Current Behavior
server
standalone with config
dataCoord:
enableActiveStandby: true
indexCoord:
enableActiveStandby: true
log:
level: debug
queryCoord:
enableActiveStandby: true
rootCoord:
enableActiveStandby: true
woodpecker:
logstore:
logFileSyncPolicy:
maxInterval: 200
storage:
type: local
client tests
- create a collection with fields: int64pk + 768dim float vector
- insert with batch 1000 concurrent 30, part insert failed
[2025-05-13T08:56:25Z] [60s] Interval Inserts: 1312000, RPS: 21866.67, Avg: 1342.18ms, P99: 3804.00ms
[2025-05-13T08:57:25Z] [120s] Interval Inserts: 1038000, RPS: 17300.00, Avg: 1627.38ms, P99: 4490.00ms
[2025/05/13 08:57:52.231 +00:00] [WARN] [milvusclient/common.go:63] ["retry func failed"] [retried=0] [error="code: STREAMING_CODE_INVALID_TRANSACTION_STATE, cause: invalid transaction state for operation GetWaitChan, expect TxnInFlight, current TxnCommitted"]
[2025/05/13 08:57:52.231 +00:00] [WARN] [milvusclient/common.go:63] ["retry func failed"] [retried=0] [error="code: STREAMING_CODE_INVALID_TRANSACTION_STATE, cause: invalid transaction state for operation GetWaitChan, expect TxnInFlight, current TxnCommitted"]
[2025-05-13T08:57:52Z] Insert failed: code: STREAMING_CODE_INVALID_TRANSACTION_STATE, cause: invalid transaction state for operation GetWaitChan, expect TxnInFlight, current TxnCommitted
[2025-05-13T08:57:52Z] Insert failed: code: STREAMING_CODE_INVALID_TRANSACTION_STATE, cause: invalid transaction state for operation GetWaitChan, expect TxnInFlight, current TxnCommitted
server error log:
loki logs
Expected Behavior
No response
Steps To Reproduce
Milvus Log
pods:
stand-wp-local-op-51-2069-etcd-0 1/1 Running 0 29h 10.104.33.200 4am-node36 <none> <none>
stand-wp-local-op-51-2069-milvus-standalone-5d664867bc-vk6fm 1/1 Running 0 27h 10.104.18.179 4am-node25 <none> <none>
stand-wp-local-op-51-2069-minio-594558f6d4-7v2mr 1/1 Running 0 29h 10.104.33.199 4am-node36 <none> <none>
Anything else?
No response
Metadata
Metadata
Labels
feature/streaming nodestreaming node featurestreaming node featurekind/bugIssues or changes related a bugIssues or changes related a bugseverity/criticalCritical, lead to crash, data missing, wrong result, function totally doesn't work.Critical, lead to crash, data missing, wrong result, function totally doesn't work.triage/acceptedIndicates an issue or PR is ready to be actively worked on.Indicates an issue or PR is ready to be actively worked on.
