milvus/internal/distributed
congqixia f0d0651989
Do not reset connection immediately if grpc code is Canceled or DeadlineExceeded (#27014)
We found lots of connection reset & canceled due to recent retry change
Current implementation resets connection no matter what the error code is
To sync behavior to previous retry, skip reset connection only if cancel error happens too much.

Also adds a config item for minResetInterval for grpc reset connection

Signed-off-by: Congqi Xia <congqi.xia@zilliz.com>
2023-09-13 15:01:18 +08:00
..
datacoord Flush by flush channels (#26859) 2023-09-12 21:07:19 +08:00
datanode Do not reset connection immediately if grpc code is Canceled or DeadlineExceeded (#27014) 2023-09-13 15:01:18 +08:00
indexnode Do not reset connection immediately if grpc code is Canceled or DeadlineExceeded (#27014) 2023-09-13 15:01:18 +08:00
proxy Do not reset connection immediately if grpc code is Canceled or DeadlineExceeded (#27014) 2023-09-13 15:01:18 +08:00
querycoord tikv integration (#26246) 2023-09-07 07:25:14 +08:00
querynode Do not reset connection immediately if grpc code is Canceled or DeadlineExceeded (#27014) 2023-09-13 15:01:18 +08:00
rootcoord tikv integration (#26246) 2023-09-07 07:25:14 +08:00
connection_manager_test.go Decouple basetable and componentparam (#26725) 2023-09-05 10:31:48 +08:00
connection_manager.go Replace deprecated grpc WithInsecure option (#26226) 2023-08-09 13:37:16 +08:00
OWNERS [skip ci]Update OWNERS files (#11898) 2021-11-16 15:41:11 +08:00