-
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]: [Nightly]DataNode crash reporting error syncTimestamp Failed : find no available rootcoord #25976
Comments
/assign @jiaoew1991 |
/assign @MrPresent-Han |
[2023/07/27 19:07:44.381 +00:00] [WARN] [sessionutil/session_util.go:798] ["connection lost detected, shuting down"] | | [2023/07/27 19:07:44.381 +00:00] [WARN] [sessionutil/session_util.go:464] ["session keepalive channel closed"] I believe it's because etcd perf bottleneck, resulting keep alive session expired and rootCoord exit by itself |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Timestamp has been removed now. v2.3.0 |
Is there an existing issue for this?
Environment
Current Behavior
DataNode crash reporting error syncTimestamp Failed : find no available rootcoord.
grafana link: https://grafana-ci.zilliz.cc/d/uLf5cJ3Gz/milvus2-0?orgId=1&var-datasource=prometheus&var-app_name=milvus&var-namespace=milvus-ci&var-instance=mdp-446-n&var-collection=All&var-pod=mdp-446-n-milvus-datacoord-7cdb5ddb46-62tp2&var-component=&from=1690480084424&to=1690485759491
error message:
2023-07-28T03:10:08.822864838+08:00 stdout F [2023/07/27 19:10:08.816 +00:00] [WARN] [datanode/flush_manager.go:941] ["failed to SaveBinlogPaths"] [segmentID=443149363355077541] [error="attempt #0: err: find no available datacoord, check datacoord state\n, /go/src/github.com/milvus-io/milvus/pkg/tracer/stack_trace.go:51 github.com/milvus-io/milvus/pkg/tracer.StackTrace\n/go/src/github.com/milvus-io/milvus/internal/util/grpcclient/client.go:352 github.com/milvus-io/milvus/internal/util/grpcclient.(*ClientBase[...]).ReCall\n/go/src/github.com/milvus-io/milvus/internal/distributed/datacoord/client/client.go:129 github.com/milvus-io/milvus/internal/distributed/datacoord/client.wrapGrpcCall[...]\n/go/src/github.com/milvus-io/milvus/internal/distributed/datacoord/client/client.go:325 github.com/milvus-io/milvus/internal/distributed/datacoord/client.(*Client).SaveBinlogPaths\n/go/src/github.com/milvus-io/milvus/internal/datanode/flush_manager.go:909 github.com/milvus-io/milvus/internal/datanode.flushNotifyFunc.func1.1\n/go/src/github.com/milvus-io/milvus/pkg/util/retry/retry.go:40 github.com/milvus-io/milvus/pkg/util/retry.Do\n/go/src/github.com/milvus-io/milvus/internal/datanode/flush_manager.go:908 github.com/milvus-io/milvus/internal/datanode.flushNotifyFunc.func1\n/go/src/github.com/milvus-io/milvus/internal/datanode/flush_task.go:205 github.com/milvus-io/milvus/internal/datanode.(*flushTaskRunner).waitFinish\n/usr/local/go/src/runtime/asm_amd64.s:1571 runtime.goexit\n: attempt #1: find no available datacoord, check datacoord state: attempt #2: find no available datacoord, check datacoord state: attempt #3: find no available datacoord, check datacoord state: attempt #4: find no available datacoord, check datacoord state: attempt #5: find no available datacoord, check datacoord state: attempt #6: find no available datacoord, check datacoord state: attempt #7: find no available datacoord, check datacoord state: attempt #8: find no available datacoord, check datacoord state: attempt #9: find no available datacoord, check datacoord state: attempt #10: find no available datacoord, check datacoord state: attempt #11: find no available datacoord, check datacoord state: attempt #12: find no available datacoord, check datacoord state: attempt #13: find no available datacoord, check datacoord state: attempt #14: find no available datacoord, check datacoord state: attempt #15: find no available datacoord, check datacoord state: attempt #16: find no available datacoord, check datacoord state: attempt #17: find no available datacoord, check datacoord state: attempt #18: find no available datacoord, check datacoord state: attempt #19: find no available datacoord, check datacoord state: attempt #20: find no available datacoord, check datacoord state: attempt #21: find no available datacoord, check datacoord state: attempt #22: find no available datacoord, check datacoord state: attempt #23: find no available datacoord, check datacoord state: attempt #24: find no available datacoord, check datacoord state: attempt #25: find no available datacoord, check datacoord state: attempt #26: find no available datacoord, check datacoord state: attempt #27: find no available datacoord, check datacoord state: attempt #28: find no available datacoord, check datacoord state: attempt #29: find no available datacoord, check datacoord state: attempt #30: find no available datacoord, check datacoord state: attempt #31: find no available datacoord, check datacoord state: attempt #32: find no available datacoord, check datacoord state: attempt #33: find no available datacoord, check datacoord state: attempt #34: find no available datacoord, check datacoord state: attempt #35: find no available datacoord, check datacoord state: attempt #36: find no available datacoord, check datacoord state: attempt #37: find no available datacoord, check datacoord state: attempt #38: find no available datacoord, check datacoord state: attempt #39: find no available datacoord, check datacoord state: attempt #40: find no available datacoord, check datacoord state: attempt #41: find no available datacoord, check datacoord state: attempt #42: find no available datacoord, check datacoord state: attempt #43: find no available datacoord, check datacoord state: attempt #44: find no available datacoord, check datacoord state: attempt #45: find no available datacoord, check datacoord state: attempt #46: find no available datacoord, check datacoord state: attempt #47: context canceled: attempt #48: context canceled: attempt #49: context canceled"]
2023-07-28T03:10:08.830866717+08:00 stderr F panic: attempt #0: err: find no available datacoord, check datacoord state
2023-07-28T03:10:08.830890559+08:00 stderr F , /go/src/github.com/milvus-io/milvus/pkg/tracer/stack_trace.go:51 github.com/milvus-io/milvus/pkg/tracer.StackTrace
2023-07-28T03:10:08.830899292+08:00 stderr F /go/src/github.com/milvus-io/milvus/internal/util/grpcclient/client.go:352 github.com/milvus-io/milvus/internal/util/grpcclient.(*ClientBase[...]).ReCall
2023-07-28T03:10:08.83090431+08:00 stderr F /go/src/github.com/milvus-io/milvus/internal/distributed/datacoord/client/client.go:129 github.com/milvus-io/milvus/internal/distributed/datacoord/client.wrapGrpcCall[...]
2023-07-28T03:10:08.830913422+08:00 stderr F /go/src/github.com/milvus-io/milvus/internal/distributed/datacoord/client/client.go:325 github.com/milvus-io/milvus/internal/distributed/datacoord/client.(*Client).SaveBinlogPaths
2023-07-28T03:10:08.830917496+08:00 stderr F /go/src/github.com/milvus-io/milvus/internal/datanode/flush_manager.go:909 github.com/milvus-io/milvus/internal/datanode.flushNotifyFunc.func1.1
Expected Behavior
pass
Steps To Reproduce
No response
Milvus Log
Anything else?
No response
The text was updated successfully, but these errors were encountered: