Filebeat memory usage of their Agent increases continuously until it becomes unresponsive and they restart the Agent, after which this behavior repeats. Based on the hprof data, looks like S3 integration consumes up to 10GB memory, mostly from GetStates. Similar behavior in performance testing @zmoog did with aws-s3 input in polling mode: zmoog/public-notes#77
Filebeat memory usage of their Agent increases continuously until it becomes unresponsive and they restart the Agent, after which this behavior repeats. Based on the hprof data, looks like S3 integration consumes up to 10GB memory, mostly from
GetStates. Similar behavior in performance testing @zmoog did with aws-s3 input in polling mode: zmoog/public-notes#77