lighthouse/beacon_node/network/src/sync/range_sync
Divma cfd26d25e0 do not count sync batch attempts when peer is not at fault (#3245)
## Issue Addressed
currently we count a failed attempt for a syncing chain even if the peer is not at fault. This makes us do more work if the chain fails, and heavily penalize peers, when we can simply retry. Inspired by a proposal I made to #3094 

## Proposed Changes
If a batch fails but the peer is not at fault, do not count the attempt
Also removes some annoying logs

## Additional Info
We still get a counter on ignored attempts.. just in case
2022-06-07 02:35:56 +00:00
..
batch.rs do not count sync batch attempts when peer is not at fault (#3245) 2022-06-07 02:35:56 +00:00
block_storage.rs Correctly update range status when outdated chains are removed (#2827) 2021-11-26 01:13:49 +00:00
chain_collection.rs do not count sync batch attempts when peer is not at fault (#3245) 2022-06-07 02:35:56 +00:00
chain.rs do not count sync batch attempts when peer is not at fault (#3245) 2022-06-07 02:35:56 +00:00
mod.rs do not count sync batch attempts when peer is not at fault (#3245) 2022-06-07 02:35:56 +00:00
range.rs keep failed finalized chains to avoid retries (#3142) 2022-04-13 01:10:55 +00:00
sync_type.rs Sync wrong dbg assertion (#2821) 2021-11-19 02:38:25 +00:00