When orchard is deployed behind an AWS NLB, the output is flooded with messages similar to the below due to TCP probing:
2023/07/05 20:33:34 http: TLS handshake error from 172.16.10.15:2378: EOF
2023/07/05 20:33:34 http: TLS handshake error from 172.16.1.30:11674: EOF
2023/07/05 20:33:34 http: TLS handshake error from 172.16.5.93:2002: EOF
The issue is described on https://github.com/golang/go/issues/26918 and the suggested workaround is to filter out those messages at the application level. Is this something you'd consider?
Hi @fkorotkov,
When orchard is deployed behind an AWS NLB, the output is flooded with messages similar to the below due to TCP probing:
The issue is described on https://github.com/golang/go/issues/26918 and the suggested workaround is to filter out those messages at the application level. Is this something you'd consider?