Embed Notice

@lanodan you know what? I'm curious about that too.

It was haproxy writiing logs to stdout in O_NONBLOCK mode. If a write fails, haproxy drops logs. As soon as I set nbthread > 1, it started dropping logs.

Now where did that stdout go? IIRC through a pipe to containerd (or kubelet or runc or sth) that was copying those logs to files in /var/log, which were then being tailed by fluentd, which tried to parse timings and couldn't keep up.

1/