Hi,
In my case, the ‘Connection reset by peer’ issue was related timeout settings of client and gcp resources.
In the condition with Reactor Netty version: 1.0.10 and Spring boot version: 2.5.4, the existing channel is disconnected and a new channel is created when a request occurs after 10 minutes of idle time. The service was modified by adjusting the setting value for connection.
Note that the HTTP LB timeout and keepalive timeout values for GCP cannot be changed to 10 minutes.
And when the connection is terminated in LB, the connection of the client is also terminated, and an error occurs when a new request occurs at that time, so we set the maximum interval setting less than 10 minutes, which is LB’s idle timeout
Depending on the client configuration or environmental conditions, this may not be the right answer. You need to configure a testable environment and change the settings to different conditions.