Open NicoYuan1986 opened 2 hours ago
/assign @chyezh /unassign
The panic info is reported when etcd-initializing, the etcd is not ready. So it's not the cause of test failure.
action with pulsar topic failure:
[2024/09/19 19:23:55.001 +00:00] [WARN] [timetick/timetick_sync_operator.go:84] ["send time tick sync message failed"] [pchannel="{\"Name\":\"by-dev-rootcoord-dml_7\",\"Term\":2}"] [error="append time tick msg to wal failed, timestamp: 452663381635105769, previous message counter: 100: message send timeout: TimeoutError"] [errorVerbose="append time tick msg to wal failed, timestamp: 452663381635105769, previous message counter: 100: message send timeout: TimeoutError\n(1) attached stack trace\n -- stack trace:\n | github.com/milvus-io/milvus/internal/streamingnode/server/wal/interceptors/timetick.(*timeTickSyncOperator).sendPersistentTsMsg\n | \t/workspace/source/internal/streamingnode/server/wal/interceptors/timetick/timetick_sync_operator.go:218\n | github.com/milvus-io/milvus/internal/streamingnode/server/wal/interceptors/timetick.(*timeTickSyncOperator).sendTsMsg\n | \t/workspace/source/internal/streamingnode/server/wal/interceptors/timetick/timetick_sync_operator.go:200\n | github.com/milvus-io/milvus/internal/streamingnode/server/wal/interceptors/timetick.(*timeTickSyncOperator).Sync\n | \t/workspace/source/internal/streamingnode/server/wal/interceptors/timetick/timetick_sync_operator.go:76\n | github.com/milvus-io/milvus/internal/streamingnode/server/wal/interceptors/timetick/inspector.(*timeTickSyncInspectorImpl).background.func1\n | \t/workspace/source/internal/streamingnode/server/wal/interceptors/timetick/inspector/impls.go:75\n | github.com/milvus-io/milvus/internal/streamingnode/server/wal/interceptors/timetick/inspector.(*timeTickSyncInspectorImpl).background.(*ConcurrentMap[...]).Range.func3\n | \t/workspace/source/pkg/util/typeutil/map.go:54\n | sync.(*Map).Range\n | \t/usr/local/go/src/sync/map.go:476\n | github.com/milvus-io/milvus/pkg/util/typeutil.(*ConcurrentMap[...]).Range\n | \t/workspace/source/pkg/util/typeutil/map.go:51\n | github.com/milvus-io/milvus/internal/streamingnode/server/wal/interceptors/timetick/inspector.(*timeTickSyncInspectorImpl).background\n | \t/workspace/source/internal/streamingnode/server/wal/interceptors/timetick/inspector/impls.go:74\n | runtime.goexit\n | \t/usr/local/go/src/runtime/asm_amd64.s:1650\nWraps: (2) append time tick msg to wal failed, timestamp: 452663381635105769, previous message counter: 100\nWraps: (3) message send timeout: TimeoutError\nError types: (1) *withstack.withStack (2) *errutil.withPrefix (3) *pulsar.Error"]
Is there an existing issue for this?
Environment
Current Behavior
Streaming service is not stable and crash during nightly tests. link: https://jenkins.milvus.io:18080/blue/organizations/jenkins/Milvus%20Nightly%20CI(new)/detail/master/122/pipeline/139/
The test ended with failure:
Maybe the crash has something wrong with bitmap.
Expected Behavior
pass
Steps To Reproduce
No response
Milvus Log
panic log: artifacts-milvus-distributed-streaming-service-mdss-master-122-py-n-122-e2e-logs.tar.gz
grafana link: https://grafana-4am.zilliz.cc/d/uLf5cJ3Ga/milvus2-0?orgId=1&from=1726771890361&to=1726778674656&var-datasource=P1809F7CD0C75ACF3&var-namespace=milvus-ci&var-instance=mdss-master-122-py-n&var-collection=All&var-app_name=milvus
Anything else?
No response