What is the default server streaming timeout (xhr.timeout) and how to modify it?

[kanekv]

[sampajano]

@kanekv Hi :)

I think you might be able to specify the timeout in Envoy config: example, if that's the proxy you're using.

[kanekv]

@sampajano Client is terminating the stream, there is no timeout on the server, if I connect from another client stream can last forever. From the browser it is terminated within 5-8 minutes. I wonder where this timeout is set.

[sampajano]

Aha ok thanks for clarifying!

I'm guess you're not setting any deadline here?
https://github.com/grpc/grpc-web#setting-deadline

As far as i understand from reading our code, the client should respect the above-mentioned deadline, but otherwise doesn't try to specify a XHR timeout:

grpc-web/javascript/net/grpc/web/grpcwebclientbase.js

Lines 326 to 345 in 49d3b70

	if (xhr.headers.has('deadline')) {
	const deadline = Number(xhr.headers.get('deadline')); // in ms
	const currentTime = (new Date()).getTime();
	let timeout = Math.ceil(deadline - currentTime);
	xhr.headers.delete('deadline');
	if (timeout === Infinity) {
	// grpc-timeout header defaults to infinity if not set.
	timeout = 0;
	}
	if (timeout > 0) {
	xhr.headers.set('grpc-timeout', timeout + 'm');
	// Also set timeout on the xhr request to terminate the HTTP request
	// if the server doesn't respond within the deadline. We use 110% of
	// grpc-timeout for this to allow the server to terminate the connection
	// with DEADLINE_EXCEEDED rather than terminating it in the Browser, but
	// at least 1 second in case the user is on a high-latency network.
	xhr.setTimeoutInterval(Math.max(1000, Math.ceil(timeout * 1.1)));
	}
	}
	}

Maybe you could try specifying the deadline and see if it's honored? it might help us narrow down the search.

[kanekv]

@sampajano that seems to be for unary calls. How do we do that for server streaming?

[sampajano]

@sampajano that seems to be for unary calls. How do we do that for server streaming?

Ah right. Although this is the only occurrence in our codebase that calls xhr.setTimeoutInterval so i don't see how we're doing it for server streaming also.

Client is terminating the stream, there is no timeout on the server, if I connect from another client stream can last forever.

I wonder how did you determine that client is terminating the stream?

If you connect from another grpc client, you'd likely not be using grpc-web, and also not Envoy. And that's why i suspected that Envoy was terminating the request originally.