You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have several instances of Seq. Each with a replicator app instance. On an Seq instance that receives no ingested traffic, the memory used by the replicator app grows continuously.
Eventually, may take several months, the memory usage will use the majority of the hosts memory. Forcing the replicator app to reload, by force updating it, will release the memory.
On Seq instances that receive traffic, this does not occur.
The text was updated successfully, but these errors were encountered:
Thanks for the note, @williamb1024. This sounds a lot like serilog/serilog-sinks-periodicbatching#76, but as far as I can tell, the app is using an earlier version of that codebase. I think updating to Serilog.Sinks.Seq 9.0.0 here would be my first attempt at a fix anyway, so we'll do that when we have a spare moment and re-publish this package.
I have several instances of Seq. Each with a replicator app instance. On an Seq instance that receives no ingested traffic, the memory used by the replicator app grows continuously.
Eventually, may take several months, the memory usage will use the majority of the hosts memory. Forcing the replicator app to reload, by force updating it, will release the memory.
On Seq instances that receive traffic, this does not occur.
The text was updated successfully, but these errors were encountered: