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.
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.