My first server crash in 24 hours just happened. So, I looked at the logs.
Someone performed quick, local searches on my peer. One of their search queries:
yacy.space
Yacy then complied with admin settings and temporarily blocked an IP address from rapid-fire local searches. The IP address:
This redirects to yacy.space.
For now, my firewall is blocking that IP address, in an effort to reduce server crashes.
ufw insert 1 deny from 157.245.217.151
I had a look and between codex and myself, we found out what was causing the crashes:
Close owned remote Solr HTTP clients - #809
Basically, in certain circumstances, yacy opens a thread to handle a new process, and when it is done, it doesn’t close the thread. When one of my nodes crashed, there were almost 39,000 threads left open, not on purpose. It hit the hard thread limit specified in systemd, and couldn’t create any new ones. After running a couple of nodes with the code patch in place for about 24 hours, and 5000-6000 searches on each from yacy.space:
Current counts:
… before the code change the Connection evic count was 38,393 in only a few hours, so it looks like it is now properly releasing the threads it no longer needs, adn we have this one issue beat. Hope @Orbiter sees it the same way. 
Anyone knows when a new official YaCy release get’s pushed?
