You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi Team - is there a resource leak issue with the concurrent interceptor? I am trying it for a java application and the qps just dies after sometime. Is it a know issue?
The text was updated successfully, but these errors were encountered:
Just to close this thread, the resource leak was resulting from grpc-java behavior where it drops the response in case grpc executor queue is full. When the response is dropped, grpc stack doesn't ensure any callback/notification which can be intercepted and the initial concurrent interceptor resource like semaphore used by request gets leaked. The solution is to keep executor queue big enough to prevent the behavior.
grpc-java issue grpc/grpc-java#636
Hi Team - is there a resource leak issue with the concurrent interceptor? I am trying it for a java application and the qps just dies after sometime. Is it a know issue?
The text was updated successfully, but these errors were encountered: