Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

s3: workaround on-reload memleak when no role is set #5149

Merged
merged 3 commits into from
Oct 3, 2024

Conversation

HofiOne
Copy link
Collaborator

@HofiOne HofiOne commented Oct 2, 2024

syslog-ng leaks an amount of memory every time it's reloaded if an s3 destination is configured. As a quick workaround we partially revert the patch introducing the use of boto3.Session when no role() is set.

Backport of 318 by @orymate

orymate and others added 2 commits October 2, 2024 16:39
AxoSyslog leaks an amount of memory every time it's reloaded if an s3
destination is configured. As a quick workaround we partially revert the
patch introducing the use of `boto3.Session` when no `role()` is set.

Signed-off-by: Mate Ory <mate.ory@axoflow.com>
Signed-off-by: Attila Szakacs <attila.szakacs@axoflow.com>
Signed-off-by: Hofi <hofione@gmail.com>
@HofiOne HofiOne merged commit 1c3520a into syslog-ng:master Oct 3, 2024
25 checks passed
@HofiOne HofiOne deleted the s3-memleak-fix branch October 3, 2024 10:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants