Today all the document counts for the sixcooler servers were reset to zero. I hope whoever runs it can get it fixed. ![]()

Today all the document counts for the sixcooler servers were reset to zero. I hope whoever runs it can get it fixed. ![]()

It’s possible the admin is performing an upgrade or maintenance cycle, as this has happened before.
Hopefully everything will repopulate once the peers finish syncing.
It looks like a temporary reset rather than data loss.
It takes time to export / import Data the size of the problem being around ~2 TB per peer.
My current system would take estimated 65 hours per peer to backup to another system with the hardware I have.
It looks like you were right. I checked again and now the six-pack (minus one) climbed back up to its high document count.

Your agent-smokingwheels is almost at the same document count. ![]()
I feel honored that my nodes are being watched so closely. ![]()
I run a setup where per ‘sixcooler’ is the only one having the solr index running and serving to the small sixcooler[1-4] peers.
Whenever sixcooler crashes - it is like this until I sart yacy on sixcooler again
I appreciate your work on the network.
This is where your server status was visible for me, making it easy to see a peer’s current document count and availability: http://filsofia.com/skip.php
Thanks for you nodes, @sixcooler! They apparently keep a large part of index alive.
What hardware do you use? Do you have some special configuration recommendation?