In case of Server-Side streaming where analytics data is streamed back to client, is it possible to configure the maximum size of buffer that can be used by that RPC call?
Currently I could see that the buffer size keeps on increasing until OOM occurs if client disconnects and server couldn't send back the response. Even though manual flow control is possible for each RPC implementation, looking for an option to tweak it at configuration level or at Interceptor level to make sure such orphaned/rouge RPC calls are discarded in a better way.
In case of Server-Side streaming where analytics data is streamed back to client, is it possible to configure the maximum size of buffer that can be used by that RPC call?
Currently I could see that the buffer size keeps on increasing until OOM occurs if client disconnects and server couldn't send back the response. Even though manual flow control is possible for each RPC implementation, looking for an option to tweak it at configuration level or at Interceptor level to make sure such orphaned/rouge RPC calls are discarded in a better way.