At least in my case it’s neither a snapshot nor replication task. I actually have the feeling the GUI is involved. I will let the system run without logging into the GUI for a while to check.
After 7h: no issues so far
service middlewared status | grep PID | grep -Po “\d+” | xargs -o htop -p
After 12h: no issues
After 24h: still no issues
and now let’s restart middlewared, click around in the GUI for 10 minutes, just going through the settings without actually changing stuff, log out again and wait another 5 minutes:
And suddenly you have +10% CPU usage and about the same RAM usage as if the system would have been running for 24h without touching the GUI.
Oh well, opened a ticket - got closed without even any comment and pointing me to the board to seek assistance - you are joking, right ? So obviously that’s not a bug but a feature and not even worth looking into. Ok then - lets fall back to restarting middlewared each time i used the gui or just do a daily restart via cron - impact solved, problem still existing and probably the one and only bug report i ever filed, as it seems to be pretty much a waste of time…