Closed wangting0128 closed 10 months ago
/assign @chyezh could you help on investigating this?
/unassign
A timeout (context.DeadlineExceed) during the search process cause that the Proxy component to perform a GRPC reconnection to local rootCoord. The error was recovered by one seconds. There's no more log context on rootCoord to find the cause of the problem. It may be just a network error. A merged PR https://github.com/milvus-io/milvus/pull/27101 has been optimized the reconnection logic. I think this issue can be closed and wait for reproducing, then reopen. @wangting0128
A timeout (context.DeadlineExceed) during the search process cause that the Proxy component to perform a GRPC reconnection to local rootCoord. The error was recovered by one seconds. There's no more log context on rootCoord to find the cause of the problem. It may be just a network error. A merged PR #27101 has been optimized the reconnection logic. I think this issue can be closed and wait for reproducing, then reopen. @wangting0128
@elstic Please follow up on this issue
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.
Rotten issues close after 30d of inactivity. Reopen the issue with /reopen
.
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.
Rotten issues close after 30d of inactivity. Reopen the issue with /reopen
.
Is there an existing issue for this?
Environment
Current Behavior
argo task: new-stable-master-1694293200 client pod: new-stable-master-1694293200-2313532893
server:
client logs:
test result:
Expected Behavior
No response
Steps To Reproduce
Milvus Log
Milvus log:
Anything else?
No response