Closed rekby closed 7 months ago
YDB GO SDK version: 3.55.0
A lot of goroutines with stacktrace:
goroutine 22945997 [select, 4 minutes]: google.golang.org/grpc/internal/grpcsync.(*CallbackSerializer).run(0xc00202c5e0, {0x179f0f8, 0xc002e9f950}) .../vendor/google.golang.org/grpc/internal/grpcsync/callback_serializer.go:83 +0x112 created by google.golang.org/grpc/internal/grpcsync.NewCallbackSerializer in goroutine 22945995 .../vendor/google.golang.org/grpc/internal/grpcsync/callback_serializer.go:55 +0x129
Reproduce:
iptables -A OUTPUT -p tcp --dport 2135 -j DROP ip6tables -A OUTPUT -p tcp --dport 2135 -j DROP
It can happens if sdk doesn't close old grpc.Conn
Need close idle https://github.com/ydb-platform/ydb-go-sdk/issues/1044
It is not leak, but keep alive a lot of idle connections. https://github.com/ydb-platform/ydb-go-sdk/issues/1146
Bug Report
YDB GO SDK version: 3.55.0
A lot of goroutines with stacktrace:
Reproduce:
It can happens if sdk doesn't close old grpc.Conn