➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Oleg Nykolyn
Recipients Oleg Nykolyn, remi.lapeyre, serhiy.storchaka, vinay.sajip
Date 2020-10-14.15:36:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1602689785.49.0.933635775811.issue40352@roundup.psfhosted.org>
In-reply-to
Content 
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
History
Date User Action Args
2020-10-14 15:36:25Oleg Nykolynsetrecipients: + Oleg Nykolyn, vinay.sajip, serhiy.storchaka, remi.lapeyre
2020-10-14 15:36:25Oleg Nykolynsetmessageid: <1602689785.49.0.933635775811.issue40352@roundup.psfhosted.org>
2020-10-14 15:36:25Oleg Nykolynlinkissue40352 messages
2020-10-14 15:36:25Oleg Nykolyncreate