if it cannot provide a small part of the piece within 15 seconds, now it’s considered as incredible slow. It would be audited for the same piece three more times (instead of two in a previous implementation). If it would fail, well, this audit will be failed. Time to change something in your setup I would assume.
This is a goal. Currently you have 12 days offline before suspension. But please, fix the issue as soon as possible. Every offline hour costs your node several GBs of stored data.
Perhaps. But even for 5 minutes timeout we didn’t have this. Maybe it’s a time, but I’m not sure yet.
Then your node is passed this audit.
It’s explained in the blueprint which I linked before. But in short - to reduce the load on your node to allow it to pass the audit.
Perhaps. But the audit frequency is definitely lower than the default readability check frequency (it’s happening every 1m0s by default). Maybe your node could be overloaded right now, but not when the audit request is to come.
You are welcome! Yes, it’s confusing me as well… However, I’m aware of it and always point out to this:
It can, if your node didn’t lose these pieces. Every successful audit will increase the audit score.