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
Now if slot 3 has more than MAX_REPAIR_LENGTH number of shreds (very probable after a partition, it's all ticks), then there's a chance another validator trying to repair could be missing more than MAX_REPAIR_LENGTH shreds in slot 3. Because repair searches for missing slots starting from the root, in order, then it'll saturate all its repair bandwidth at slot 3, and never try to repair the main fork
Proposed Solution
Weight forks based on number of validators that have
> 34% confirmed a fork
If not 1), then number of validators that have completed the fork
The text was updated successfully, but these errors were encountered:
Problem
Repairs have a limited quota of requests per iteration, which can be exhausted on a dead fork.
For example imagine a fork structure that looks something like:
Now if slot 3 has more than MAX_REPAIR_LENGTH number of shreds (very probable after a partition, it's all ticks), then there's a chance another validator trying to repair could be missing more than MAX_REPAIR_LENGTH shreds in slot 3. Because repair searches for missing slots starting from the root, in order, then it'll saturate all its repair bandwidth at slot 3, and never try to repair the main fork
Proposed Solution
Weight forks based on number of validators that have
> 34%
confirmed a forkThe text was updated successfully, but these errors were encountered: