Oleg Nykolyn <jurav...@gmail.com> added the comment:
There are multiple servers running in Kubrnetes cluster - API servers based on Django, celery workers, etc. All of them send logs to AWS TCP balancer, which acts as balancer for vector service[1], which send logs to Elasticsearch. Basically we have following logging pipeline: python-based services -> AWS TCP network balancer -> vector -> Elasticsearch. AWS network balancer has an option called "Idle timeout" with max value of 3600 seconds[2]. Log messages are logged successfully at first, but fail(one message gets lost on re-connect) if there is gap between messages, corresponding to "Idle timeout". 1: https://github.com/timberio/vector 2: https://docs.aws.amazon.com/elasticloadbalancing/latest/network/network-load-balancers.html#connection-idle-timeout ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue40352> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
