nodejs/node

http socket might get reset instead of normal close while handling timeout

Open

#26.166 aberto em 17 de fev. de 2019

Ver no GitHub
 (5 comments) (5 reactions) (0 assignees)JavaScript (35.535 forks)batch import
help wantedhttpstale

Métricas do repositório

Stars
 (117.218 stars)
Métricas de merge de PR
 (Mesclagem média 18d 17h) (219 fundiu PRs em 30d)

Description

  • Version: v10.15.1
  • Platform: Linux 0fe3a1d57e94 4.9.125-linuxkit #1 SMP Fri Sep 7 08:20:28 UTC 2018 x86_64 GNU/Linux
  • Subsystem: http,net

We were experiencing unexpected dropped connections between AWS ALB and nodejs application resulting in 502 errors from load balancer.

Managed to replicate a condition when nodejs abnormally closes socket with RST packet instead of normal FIN packets.

Here's exact conditions:

server.timeout = 10 * 1000;
server.keepAliveTimeout = 0;

image

We kept doing requests to the same connection every 10 seconds to trigger the condition.

Note that data was received and acknowledged, but instead of handling data or closing socket in a normal way nodejs reset the tcp connection.

Guia do colaborador