You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently if the assigned validator fails to relay a message it is simply removed from the queue and does not count as a failure to the assigned validator. This means if a validator is incapable or unwilling to relay messages, it's success rate metric never changes.
When removing messages from the queue, we need to check if it was relayed (it has public or error data). If it does not, then we need to consider it a failure and update the validator metrics.
The text was updated successfully, but these errors were encountered:
# Related Github tickets
- ClosesVolumeFi#2173
# Background
Currently if the assigned validator fails to relay a message it is
simply removed from the queue and does not count as a failure to the
assigned validator. This means if a validator is incapable or unwilling
to relay messages, it's success rate metric never changes.
When removing messages from the queue, we check if it was relayed (it
has public or error data). If it does not, then we consider it a failure
and update the validator metrics.
# Testing completed
- [x] test coverage exists or has been added/updated
- [x] tested in a private testnet
# Breaking changes
- [x] I have checked my code for breaking changes
- [x] If there are breaking changes, there is a supporting migration.
Currently if the assigned validator fails to relay a message it is simply removed from the queue and does not count as a failure to the assigned validator. This means if a validator is incapable or unwilling to relay messages, it's success rate metric never changes.
When removing messages from the queue, we need to check if it was relayed (it has public or error data). If it does not, then we need to consider it a failure and update the validator metrics.
The text was updated successfully, but these errors were encountered: