Question about Envoy Buffers (Istio+gRPC)

unread,

May 27, 2020, 3:47:37 AM5/27/20

to envoy-users

We are currently using Istio + Envoy + Bi-Directional gRPC Streaming APIs.

We have configured Envoy buffer size ~ 64-128K for our workload.

During Istio + Envoy upgrade, Envoy buffer gets wiped out and the data is lost (considering that client is unable to do retries in certain cases).

Hence the question is: does Envoy support persistence to the data in this buffer or is there any plan for it in the future?

If not, any recommendations on how to avoid data loss during Istio+Envoy upgrades ?

unread,

Jun 7, 2020, 11:01:15 PM6/7/20

to envoy-users

Checking again, if anybody has any recommendations ?

unread,

Jun 8, 2020, 6:52:31 PM6/8/20

to envoy-users

How are you setting these buffers?

On Wednesday, May 27, 2020 at 12:47:37 AM UTC-7, salo wrote:

unread,

Jun 21, 2020, 11:46:41 PM6/21/20

to envoy-users

Buffer size is set by using NettyChannelBuilder.flowControlWindow in gRPC

And in Envoy using:

Http2ProtocolOptions:

initial_stream_window_size

initial_connection_window_size

Thanks,

Reply all

Reply to author

Forward