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

[BUG] Uncontrolled growth of memory consumption #420

Open
XCiteForever opened this issue Aug 14, 2024 · 1 comment · May be fixed by #446
Open

[BUG] Uncontrolled growth of memory consumption #420

XCiteForever opened this issue Aug 14, 2024 · 1 comment · May be fixed by #446
Labels
bug Something isn't working

Comments

@XCiteForever
Copy link

ECS integration/library project(s) (e.g. Elastic.CommonSchema.Serilog): Elastic.Extensions.Logging

ECS schema version (e.g. 1.4.0): latest

ECS .NET assembly version (e.g. 1.4.2): latest

.NET framework / OS: .NET 8.0 / Any OS

Setting OutboundBufferMaxLifetime to Timespan.Zero will cause memory consumption to continually increase.

Steps to reproduce:
1.
Configure connection as:
services .AddLogging(c => { c.AddElasticsearch(lo => {}, co => { co.BufferOptions.OutboundBufferMaxLifetime = TimeSpan.Zero; }); });
image

@XCiteForever XCiteForever added the bug Something isn't working label Aug 14, 2024
@Mpdreamz
Copy link
Member

Mpdreamz commented Sep 17, 2024

I couldn't quite reproduce this but because TimeSpan.Zero basically causes export buffers of size 1 the inbound channel will never be drained fast enough and so should grow although not bounded.

I opened elastic/elastic-ingest-dotnet#72 to address this.

Will spend some more time trying to reproduce.

@Mpdreamz Mpdreamz linked a pull request Sep 18, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants