- 최신
- 최다 투표
- 가장 많은 댓글
For Classic Load Balancer, TCP keep-alives will not keep the connection alive. HTTP payload is required for the connection to be alive for Classic Load Balancers.
With Network Load Balancer, the TCP keep-alives can prevent the connection from reaching the idle timeout. However, the keep-alives must be enabled in both directions. If the server sends a keep-alive message, the client has to respond with a keep-alive acknowledgment. If the clients are unresponsive to keep-alives from the server, the idle timeout of 350 seconds will be reached. If either endpoint (client or server) sends traffic to the idle connection, Network load Balancer will generate a reset.
The HTTP payload will also keep the connection alive in case of NLB however you will have to make sure that it is being sent before hitting the 350sec timeout.