Relates to: #567

We are running the live demo in a droplet with 1GB of RAM.

The tracker domain is https://tracker.torrust-demo.com/health_check.

On the 29th of December I changed the tracker configuration from

remove_peerless_torrents = true

To:

remove_peerless_torrents = false

With this change, the tracker does not clean up torrents without peers. That makes the data structure containing the torrent data grow indefinitely.

That makes the process to run out of memory every 5 hours approx:

I guess, the Tracker container crashes and it's restarted again, otherwise I suppose the process would simply die.

We should limit the memory usage. This could happen even with the option remove_peerless_torrents enabled.

cc @WarmBeer @da2ce7

Last 24 hours

Last 7 days