Michael Pratt 1bc3afc5d3 deploy: increase coordinator ingress timeout to 24 hours ... Connections connected for long than the timeout are automatically closed by the load balancer. gomote create (CreateInstance) and gomote run (ExecuteCommand) are implemented as single, long-running gRPC calls. Currently, if one of these exceeds 2 hours, the connection is closed and the call fails. Increase the limit to 24 hr as a mitigation to give long-running commands more time to complete. As noted at https://cloud.google.com/load-balancing/docs/https#timeouts_and_retries, these connections are still at risk of reset due to restarts of the load balance itself, so ideally gomote eventually migrates to RPCs that support retry/continue. For golang/go#56423. Change-Id: Ia10faea1ca8558373d2d6b45abcf99c476317270 Reviewed-on: https://go-review.googlesource.com/c/build/+/445435 TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Run-TryBot: Michael Pratt <mpratt@google.com> Reviewed-by: Heschi Kreinick <heschi@google.com>		2022-11-02 18:49:39 +00:00
..
build-ingress.yaml	deploy: increase coordinator ingress timeout to 24 hours	2022-11-02 18:49:39 +00:00