-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs(faq): Add initial details about penalties #481
base: main
Are you sure you want to change the base?
Conversation
Ad discussed on Slack, and related to cronian-tech/saturn-moonlet#3. Signed-off-by: Michael Vorburger ⛑️ <[email protected]>
docs/faq.md
Outdated
- Fix this by resolving the root cause of the node unavailability. | ||
- Note the [deregister my node](#how-can-i-manually-deregister-my-node) section. | ||
|
||
None of these are "expected" under normal operation, and all are something that you want to keep down. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Error rates are expected. Duplicate cache misses are not, this statement isn't general
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh! OK, I have removed this phrase, but... if Error rates are expected under normal operations, then why does Node get penalized for it, if there is nothing its operator can do about it?
@DiegoRBaquero thanks for the prompt review; I've incorporated your feedback - merge this? |
Ad discussed on Slack, and related to cronian-tech/saturn-moonlet#3.
@DiegoRBaquero @AmeanAsad