Isn’t that some kind of a wormhole? Meaning: without ANY errors the node can be disqualified, if there’s no constant monitoring on the scores (besides the logs) and a fast reaction of the SNO, in case it’s being worse (ugh, my monitoring script works pretty well, I’ve recognized).
That’s really a mess, if it’s happening with a huge node and a lot of audit traffic. Because suspension will be skipped and it’s very fast disqualified.
This can be the case as well from my issues at the beginning of the year with the performance on MacOS, before I’ve switched back to RPi. Crossing fingers these are some minor hiccups over time as this one, IF that was the reason.
It would be nice if the satellite could provide some feedback (audit results), but it could help to malicious users too to improve their strategy…
However, you can create an issue to add such feedback to the storagenode’s logs.
Checked - that’s not the case: maximum time lag was 0.7 seconds.
So it must be this one.
Consequently I calm down, because:
Anyway, I’ve added the time lag analysis to the issue list of the monitoring script as well. At least I can create a routine which indicates time lags between audit requests, without the need to have it reported in the logs.
@Alexey I’ve added an automatic alert in version 1.9.0 in case time lags between audit downloads started and finished > 3 mins. Users will be notified automatically by mail and/or discord push message in order to quickly react and avoid a disqualification of their nodes. Will add it to the wiki page, too.